3.4. TC EVENTPUB

The first part of the session was a review of the extensions specification and the properties and parameters defined there. Since the last round table we’ve defined a new GROUP parameter to allow grouping of related properties. This has expected uses outside of event publication — in particular tasks. The PARTICIPANT property has now been renamed to ASSOCIATE. There were suggestions about the role of ASSOCIATE and how it relates to ATTENDEE. There are no iTIP semantics for ASSOCIATE so no broadcasting of data to potentially very large numbers of users. The specification was resubmitted at the beginning of the week and needs some review and then trying to move it on to the next stage in the IETF.

We also talked (again) about sharing and subscriptions. Of particular interest in event publication is the ability to register for a specific event. Related to that is the ability to signify interest in selected events or tasks and have those appear in the users calendar client and for that user to receive notifications of changes. Bedework implements a special collection type in which such events appear.